Blog
Recent Entries
BoxLang 1.18.0 Released : Every Cloud, Every Node, Every Agent
Azure joins the serverless family. Scheduled tasks become cluster-safe. And the whole platform gets documentation and skills built for developers and AI agents working side by side.
If you run a technology organization, you are being asked to do three things at once: ship faster, keep the estate you already have running, and make AI part of how your teams work. Most stacks make you choose. BoxLang 1.18 is another step toward not having to.
ColdBox 8.2 Deep Dive, Part 4 of 5 : AI Routing and Gateways
We've been building AI into the core of ColdBox since 8.0, because the applications teams are asked to build have changed. They talk to models, stream answers, expose tools to other AI systems, and increasingly host agents that act on behalf of users. None of that should require bespoke plumbing in every project.
Add Your Comment
(6)
Mar 19, 2013 02:18:17 UTC
by Chris Galli
event.getValue('foo','default'); is not returning as I am understanding it should. I am using
prc.isWidget = event.getValue('arguments.isWidget','false');
or
prc.isWidget = event.getValue('arguments.isWidget',false);
But both return false when my arguments.isWidget value is true
by using
if (arguments.isWidget){prc.isWidget = true;}else{prc.isWidget = false;}; I get the desired behavior.
Am I using this incorrectly?
Mar 19, 2013 02:46:43 UTC
by Brad Wood
You're misunderstanding the event.getValue() method. It is not a general purpose method for accessing any variables in the function but instead a special method specifically for getting values from the request collection. If you do event.getValue('arguments.foo') that is looking for a key called in the request collection struct, or rc[] which is obviously not what you want.
If you want to deal with values coming into the arguments scope, you want to use the regular functionality of CFML to deal with that such as CFParam, structKeyExists() and the like. Only use the methods in the event object to work with the request collection.
Mar 19, 2013 11:57:01 UTC
by Chris Galli
Thanks. That makes sense now. Something more like
param arguments.isWidget = event.getValue('rc.isWidget','false');
pr.isWidegt = arguments.isWidget;
should give the arguments scope priority while gracefully delegating to the rc and then to a default value.
Mar 19, 2013 17:27:41 UTC
by Chris Galli
I discovered I do not need to reference the rc in the event.get value.
<br><br>
param arguments.isWidget = event.getValue('isWidget','false');
<br><br>
prc.isWidget = arguments.isWidget;
Mar 19, 2013 18:00:52 UTC
by Brad Wood
Yep, I was going to comment to that effect but you beat me to it. You only have to pass in the exact name of the variable in the rc to the getValue method. Otherwise it would be looking for rc[] which wouldn't exist.
Think of it this way:
return event.getValue();
is the exact same as:
var rc = event.getCollection();
return rc.foobar;
Mar 19, 2013 18:01:44 UTC
by Brad Wood
Wow, that's annoying that all our line breaks keep getting eaten-- I'm going to put in a ticket for that :)